RE-POSTED FROM wINDOWS 7 PERFORMANCE THREAD:Hi All: I'm sitting here watching the Media Center Update log and Task Mgr as my cpu and a storage drive have been churning away (again) for the last 15 mins for a process called "Client Maintenance" in the log. This can't be the way the engineers want Win7 to work. It appears that as part of the Media Center update process that the update is occasionally followed by a very cpu/hard drive intensive defragmentation of the storage drive that Media Center is set to record to????? I sure don't think it's a wise idea for the O.S. to automatically start a defragmentation of the recording drive at random times that may coincide with other processes that also may be occurring. OK, Client Maintenance has now completed..........it took 22 minutes of my 3GHz Intel E8400 running at 50% continuously and my (G:) partition was churning at almost capacity the whole time also. I have my O.S. set to notify me but not download or install windows updates and during this time I received notice that there were 2 updates that needed installed and my anti-virus wanted to update. I need to be able to control the times that such an intensive process as this "Client Maintenance" occurs! My thought is that, if indeed, Client Maintenance is automatically de-fragging the recording drive after downloading and installing guide updates that the 2 processes should be separated? I live in Tucson and had I not been monitoring the guide download log, my PC might have been subjected to heat stress if it would have been installing windows updates, anti-virus program update, Media Center open and recording a show while I watch a show, several windows open while I surf the internet and then an automatic virus scan had started. There are too many processes that start automatically that would stress the pc in the summer especially when it is typically 80 degrees in my home. And what about the poor people who aren't running a late model 3GHz dual-core processor.......would their PC go into cpu throttling or perhaps overheat? Anyone else think that client maintenance should be de-coupled from the guide update process as I do? I read a lot of posts here that people complain about their PC churning away when they aren't even knowingly causing it with their applications. Is this perhaps one of the reasons why the PC doesn't shut down properly.......because it has to stop the "Client Maintenance"? I sure would be interested in having some other testers open the Media Center Update Log and task manager when they turn on/wake-up their PC and see if they observe the same high CPU usage during "client maintenance" and post their comments as to what occurs during the "client maintenance". It doesn't start "Client Maintenance" every guide download but does on a fairly frequent basis. Your input and opinion on this would be of interest. Thanks.